fix(autofix): Show Add Integration CTA when no coding agents installed#112625
Merged
fix(autofix): Show Add Integration CTA when no coding agents installed#112625
Conversation
The coding agent dropdown (which contains the 'Add Integration' link) was only rendered when codingAgentOptions.length > 0. This meant orgs with zero coding agent integrations had no way to discover or install one from the autofix flow. Change the guard to check whether codingAgentIntegrations is defined (i.e. the step supports coding agents) rather than whether any exist, so the dropdown with the CTA always appears on relevant steps. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Agent transcript: https://claudescope.sentry.dev/share/vM7qy1Z72d-FTlutPQFEXRVgHQcSlaKFH8eEv6_DB3M
github-actions
bot
added
the
Scope: Frontend
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 2cb111c. Configure here.
DropdownMenu defaults isDisabled=true when items is empty. Pass
isDisabled={isProcessing} explicitly so the dropdown remains clickable
when no coding agent integrations are installed, allowing users to
reach the 'Add Integration' footer CTA.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Agent transcript: https://claudescope.sentry.dev/share/wa0Z3OptkpbQPvh2KPaAfODNa6tnRIKLisMHhKhifvU
The trigger button already handles disabled state via its own
disabled={isProcessing} prop. The DropdownMenu isDisabled just needs
to override the auto-disable-on-empty-items default.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Covers the exact bug scenario: when the API returns an empty integrations list, the dropdown trigger should still render and the Add Integration CTA should be accessible. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
trevor-e
approved these changes
Apr 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The coding agent dropdown in the autofix next-step UI was gated on
codingAgentOptions.length > 0, which meant the "Add Integration" CTAlink inside the dropdown footer was only visible to orgs that already had
at least one coding agent integration installed. Orgs with zero
integrations had no way to discover or install one from the autofix flow.
Changed the guard to render the dropdown whenever
codingAgentIntegrationsis defined (i.e. the current step supports coding agents), regardless of
whether any are installed. The dropdown now shows the "Add Integration"
footer link even when empty, directing users to the integrations settings
page.
Agent transcript: https://claudescope.sentry.dev/share/PXwCZuS75XHaHSRH9gv580ohH3NWiDH8vmAajsJ010c